Support Limited Data Use in Facebook Pixel #486
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@mloar Any updates on this PR? |
Contributor
Author
|
No update yet. The CircleCI build appears to have failed because of some strange git error checking out the code rather than my changes, and I don't have access to retry the job. My company has a paid account, so I'm going to reach out to support to try to move this along. |
Contributor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR will make a
dataProcessingOptionscall beforeinitto opt-in to Limited Data Use. It will do this by default.Are there breaking changes in this PR?
No.
Any background context you want to provide?
Facebook has announced a new Limited Data Use feature that is designed to assist with compliance with the California Consumer Privacy Act (CCPA). Data tagged as Limited Data Use will only be processed by Facebook in ways that allow Facebook to fit within the definition of Service Provider under the CCPA, thus avoiding the possibility that website operators using Facebook Pixel could be considered to be "selling" data to Facebook.
During the month of July Facebook will automatically tag events coming from California as Limited Data Use. But starting in August, clients must opt-in to this behavior by making a
dataProcessingOptionscall beforeinit.Is there parity with the server-side/android/iOS integration components (if applicable)?
Facebook Pixel is only a Device - Web integration.
There are similar options in the Facebook App Events and Facebook Offline Conversions APIs, which may be of interest to those using those integrations.
Does this require a new integration setting? If so, please explain how the new setting works
This adds the
limitedDataUsesetting, a boolean which defaults to true. If this setting is true, adataProcessingOptionscall will be made instructing Facebook to apply Limited Data Use if Facebook's geolocation determines the client is in the state of California.Links to helpful docs and other external resources